RCS Business Messaging

(0 reviews)

Error Codes

Asynchronous Operational Model

AAMG acts as an Asynchronous proxy, providing separation between the Aggregator/Agent layer and the Google RCS layer to allow for faster responses and greater throughput of the service.

Because of this, some error codes will be presented on Response to the RCS Message/Event Request (synchronously), and other codes will come as part of the Delivery report.

This section shows the errors for covers the synchronous response to the request.

The following are the expected HTTP status codes that can be returned and a brief description of the reason it would be returned.

HTTP Status Code	Status Text	Meaning	Retry
200	Ok	This code indicates that the Get Capabilities request was successful, and the server has successfully processed and fulfilled the request.	N/A
202	Accepted	This code indicates that the message/event request was accepted by the AAMG gateway and queued for processing.	N/A
400	Bad Request	Missing the required parameters or incorrect format.	Permanent Fail
		The destination number provided is not included in the list of test devices.	Permanent Fail
401	Unauthorized	Client credentials not sufficient to use specific endpoint or invalid Sender Id	N/A
403	Forbidden - User	Server has understood the client's request, but it refuses to fulfill it due to the user MSISDN not found or not AT&T subscriber.	Permanent FAIL
403	Forbidden - Agent	Server has understood the client's request, but it refuses to fulfill it due to the Agent lack of permission or Agent not provisioned.	Permanent FAIL
405	Method not Supported	The Method used is not supported for example GET instead of POST.	Permanent FAIL
429	Too many requests	Quota Exceeded - Number of requests exceeded those allowed by SLA tier.	Permanent FAIL
500	Internal Server Error	The server encountered an internal error or times out.	Retry
503	Server Busy	Server is busy or unavailable.	Retry

Error Codes

Reviews